Method and apparatus for processing detnet traffic

ABSTRACT

A method and apparatus for processing DetNet traffic through the steps of receiving configuration information for configuring a DetNet node from a DetNet controller of a DetNet system and configuring a UPF, a DS-TT, and/or a NW-TT in a mobile communication system as the DetNet node are provided.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of Korean PatentApplication No. 10-2021-0172903 filed in the Korean IntellectualProperty Office on Dec. 6, 2021, Korean Patent Application No.10-2022-0026316 filed in the Korean Intellectual Property Office on Feb.28, 2022, Korean Patent Application No. 10-2022-0081912 filed in theKorean Intellectual Property Office on Jul. 4, 2022, and Korean PatentApplication No. 10-2022-0169026 filed in the Korean IntellectualProperty Office on Dec. 6, 2022, the entire contents of which areincorporated herein by reference.

BACKGROUND 1. Field of the Invention

The present disclosure relates to a method and apparatus for processingDetNet traffic in a mobile communication system.

2. Description of Related Art

As the 5G system increasingly requires high-reliability and low-latencyservices, the 5G system is integrating with Time Sensitive Networking(TSN) system. By acting as a bridge in the TSN network, the 5G systemprocesses TSN streams.

SUMMARY

Embodiments of the invention provide an application function.

Embodiments of the invention provide a TSN translator.

Embodiments of the invention provide a method for processing a DetNettraffic.

According to an embodiment, an application function is provided. Theapplication function includes: a processor and a memory, wherein theprocessor executes a program stored in the memory to perform: receivingconfiguration information for configuring a Deterministic Networking(DetNet) node from a DetNet controller in a DetNet system; andconfiguring a user plane function (UPF), a device side time sensitivenetworking translator (DS-TT), and/or a network side time sensitivenetworking (NW-TT) in a mobile communication system as the DetNet node.

In such embodiment, when configuring a UPF, a DS-TT, and/or a NW-TT in amobile communication system as the DetNet node, the processor mayperform adding the configuration information to at least one informationcontainer and transferring the at least one information container to theDS-TT and/or the NW-TT.

In such embodiment, the application function may be a DetNet applicationfunction (AF) configured to communicate the mobile communication systemwith the DetNet controller of the DetNet system.

In such embodiment, the application function may be a time sensitivecommunication time synchronization function (TSCTSF) in the mobilecommunication system.

In such embodiment, the application function may be a time sensitivenetworking (TSN) application function (AF) in the mobile communicationsystem.

In such embodiment, when receiving configuration information forconfiguring a DetNet node from a DetNet controller in a DetNet system,the processor may perform receiving the configuration information fromthe DetNet controller located in an external domain of the mobilecommunication system via a network exposure function (NEF) in the mobilecommunication system.

In such embodiment, when receiving configuration information forconfiguring a DetNet node from the DetNet controller in a DetNet system,the processor may perform receiving the configuration information fromthe DetNet controller located within a domain of an operator of themobile communication system.

In such embodiment, the processor may execute the program to furtherperform: receiving DetNet traffic information from the DetNetcontroller; and mapping a DetNet flow to a quality of service (QoS) flowof the mobile communication system based on the DetNet trafficinformation.

In such embodiment, the processor may execute the program to furtherperform sending a parameter for managing connectivity of the DetNet flowto the DS-TT and/or the NW-TT.

According to an embodiment, a time sensitive networking (TSN) translatoris provided. The TSN translator includes: a processor and a memory,wherein the processor executes a program stored in the memory toperform: receiving configuration information for configuring aDeterministic Networking (DetNet) node from a DetNet controller of aDetNet system through an application function (AF) of a mobilecommunication system; and processing a DetNet flow of the DetNet systembased on the configuration information.

In such embodiment, the TSN translator may be a device-side TSNtranslator (DS-TT) located in the device side or a network-side TSNtranslator (NW-TT) located in a user plane function (UPF) in the mobilecommunication system.

In such embodiment, the processor may execute the program to furtherperform: receiving a parameter for managing connectivity of the DetNetflow from the application function; and managing the connectivity of theDetNet flow based on the parameter.

In such embodiment, the processor may execute the program to furtherperform reporting, by the DS-TT, status information of the DetNet flowto the application function through NAS signaling when the TSNtranslator is the DS-TT.

In such embodiment, the processor may execute the program to performreporting, by the NW-TT, status information of the DetNet flow to theapplication function through the UPF when the TSN translator is theNW-TT.

According to an embodiment, a method for processing a DetNet traffic isprovided. The method includes: receiving, by an application function,configuration information for configuring a DetNet node from a DetNetcontroller in a DetNet system; and configuring, by the applicationfunction, a user plane function (user plane function, UPF), a deviceside time sensitive networking translator (DS-TT), and/or a network sidetime sensitive networking translator (NW-TT) in a mobile communicationsystem as the DetNet node.

In such embodiment, the configuring a UPF, a DS-TT, and/or a NW-TT in amobile communication system as the DetNet node may include adding theconfiguration information to at least one information container andtransferring the at least one information container to the DS-TT and/orthe NW-TT.

In such embodiment, the application function may be a time sensitivecommunication time synchronization function (TSCTSF) in the mobilecommunication system.

In such embodiment, the receiving configuration information forconfiguring a DetNet node from a DetNet controller of a DetNet systemmay include receiving, by the application function, the configurationinformation from the DetNet controller located in an external domain ofthe mobile communication system via a network exposure function (NEF)within the mobile communication system; or receiving, by the applicationfunction, the configuration information from the DetNet controllerlocated in a domain of an operator of the mobile communication system.

In such embodiment, the method may further include: receiving DetNettraffic information from the DetNet controller; and mapping a DetNetflow to a quality of service (QoS) flow of the mobile communicationsystem based on the DetNet traffic information.

In such embodiment, the method may further include transferring aparameter for managing connectivity of a DetNet flow to the DS-TT and/orthe NW-TT.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a 5G system operating as a TSN bridgeaccording to an embodiment.

FIG. 2 is a diagram illustrating a mobile communication system capableof providing time-sensitive communication and time synchronizationservice according to an embodiment.

FIG. 3 is a diagram illustrating an IP domain of a DetNet according toan embodiment.

FIG. 4 is a diagram illustrating a mobile communication system operatingas the DetNet node according to an embodiment.

FIG. 5A is a diagram illustrating a mobile communication systemincluding a TSN AF that performs a function of the DetNet AF accordingto an embodiment, FIG. 5B is a diagram illustrating a mobilecommunication system including a TSCTSF that performs a function of theDetNet AF according to an embodiment, and FIG. 5C is a diagramillustrating a mobile communication system including a DetNet AFaccording to an embodiment.

FIG. 6 is a diagram illustrating a mobile communication system and aDetNet system including a TSCTSF performing the function of the DetNetAF according to an embodiment.

FIG. 7 is a diagram illustrating a DetNet information model according toan embodiment.

FIG. 8 is a flowchart illustrating a method in which the mobilecommunication system operates as a DetNet node according to anembodiment.

FIG. 9 is a diagram illustrating information of a DetNet flow identifiedin a port of a mobile communication system according to an embodiment.

FIG. 10 is a diagram illustrating an application function according toan embodiment.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In the following detailed description, only certain embodiments of thepresent invention have been shown and described in detail with referenceto the accompanying drawing, simply by way of illustration. However, thepresent disclosure may be implemented in various different forms and isnot limited to the embodiments described herein. Further, in order toclearly describe the description in the drawing, parts not related tothe description are omitted, and similar reference numerals are attachedto similar parts throughout the specification.

Throughout the specification, a terminal may be called user equipment(UE), mobile station (MS), a mobile terminal (MT), an advanced mobilestation (AMS), a high reliability mobile station (HR-MS), a subscriberstation (SS), a portable subscriber station (PSS), an access terminal(AT), a machine type communication device (MTC device), and the like andmay also include all or some of the functions of the MS, the MT, theAMS, the HR-MS, the SS, the PSS, the AT, the UE, the MTCH device, andthe like.

Further, the base station (BS) may be called an advanced base station(ABS), a high reliability base station (HR-BS), a node B, an evolvednode B (eNodeB), an access point (AP), a radio access station (RAS), abase transceiver station (BTS), a mobile multi-hop relay (MMR)-BS, arelay station (RS) serving as a base station, a relay node (RN) servingas a base station, an advanced relay station (RS) serving as a basestation, a high reliability relay station (HR-RS) serving as a basestation, small base stations (a femto base station (femto BS), a homenode B (HNB), a home eNodeB (HeNB), a pico base station (pico BS), amacro base station (macro BS), a micro base station (micro BS), and thelike), and the like and may also include all or some of the functions ofthe ABS, the node B, the eNodeB, the AP, the RAS, the BTS, the MMR-BS,the RS, the RN, the ARS, the HR-RS, the small base stations, and thelike.

In this specification, unless explicitly described to the contrary, theword “comprises”, and variations such as “including” or “containing”,will be understood to imply the inclusion of stated elements but not theexclusion of any other elements.

In this specification, expressions described in singular can beinterpreted as singular or plural unless explicit expressions such as“one” or “single” are used.

In this specification, “and/or” includes all combinations of each and atleast one of the mentioned elements.

In this specification, terms including ordinal numbers such as first andsecond may be used to describe various configurations elements, but theelements are not limited by the terms. The terms may be only used todistinguish one element from another element. For example, a firstelement may be named a second element without departing from the rightrange of the present disclosure, and similarly, a second element may benamed a first element.

In the flowchart described with reference to the drawings in thisspecification, the order of the operations may be changed, severaloperations may be merged, certain operations may be divided, andspecific operations may not be performed.

FIG. 1 is a diagram illustrating a 5G system operating as a TSN bridgeaccording to an embodiment.

Referring to FIG. 1 , a 5G system (5GS) may operate as a single logicalTSN bridge to combine a mobile communication network and a TSN.

To combine with TSN, a TSN application function (TSN AF) may be added ina control plane of the 5G system, and a device side TSN translator(DS-TT) and a network side TSN translator (NW-TT) may be added to userequipment (UE) and a user plane function (UPF) of a user plane of the 5Gsystem, respectively.

The TSN AF may connect Centralized Network Configuration (CNC) of theTSN and the 5G system and receive TSN stream information and TSN bridgeconfiguration information from the CNC.

In addition, the TSN AF may configure TSN bridge information into PortManagement Information Container (PMIC) and Bridge ManagementInformation Container (BMIC), and then the DS-TT and the NW-TT may setup ports and bridges based on the PMIC and the BMIC. As such, the 5Gsystem may operate as a bridge in the TSN network and process TSNstreams.

FIG. 2 is a diagram illustrating a mobile communication system capableof providing time-sensitive communication and time synchronizationservice according to an embodiment.

As demands for time-sensitive communication (TSC) service based on timesynchronization in application services such as video, audio, and imageprovision increases, the core network of the mobile communication systemmay include a time sensitive communication time synchronization function(TSCTSF).

Referring to FIG. 2 , the TSCTSF may interface with a policy controlfunction (PCF) and provide the time-sensitive communication and timesynchronization services to an AF outside the network of mobileoperators through a Network Exposure Function (NEF). When the AF isinside the mobile operator's network, the TSCTSF may connect to the AFwithout the NEF. To provide the TSC service in the TSN, an Ethernetpacket data unit (PDU) session (Session) may be used. Alternatively, anInternet protocol (IP) PDU session may be used so that the TSC serviceis used as an application service. In addition, since the mobilecommunication system can support IEEE 1588 in addition to IEEE 802.1AStime synchronization operating in the TSN network, the TSCTSF in thecore network may provide a deterministic QoS-based time-sensitivecommunication and time synchronization service required by theapplication services.

FIG. 3 is a diagram illustrating an IP domain of a DetNet according toan embodiment.

As the range of the time-sensitive communication service provided by the5G system gradually expands from the TSN to the application services,supports for deterministic networking (DetNet) services, a wide-areadeterministic networking technology, may be required to overcome thelimitations of a short-range DetNet of the TSN.

The DetNet technology in IETF is a network layer (that is, L3 layer)technique that guarantees lossless delivery of deterministic flows andmaximum end-to-end latency through explicit route, resource reservation,and service protection and exists within a single control.

FIG. 3 shows a stream of the DetNet flow operating in a DetNet IPdomain. The service sub-layer may classify deterministic flows andprovide service protection functions such as lossless delivery andrearrangement by using a sequence number of the flow. The forwardingsub-layer may provide resource reservation and explicit routing fordeterministic flows, which is the basis of wide-area deterministicnetworking technology. In FIG. 3 , when a App flow is an IP packet, theApp flow may include at least one of a source IP address, a destinationIP address, an IPv6 flow label, a differentiated service code point(DSCP), a protocol, a source port, and destination port.

FIG. 4 is a diagram illustrating a mobile communication system operatingas the DetNet node according to an embodiment.

Referring to FIG. 4 , a 5G system with SBA (Service Based Architecture)may operate as a single DetNet node. According to an embodiment, theDetNet AF may be included in the control plane of the mobilecommunication system, and the DetNet AF may be connected to the PCFinside the 5G system and connected to a DetNet controller outside the 5Gsystem.

In an embodiment, the DetNet AF may be connected to the DetNetcontroller (e.g., a centralized DetNet controller) and may transmit andreceive DetNet Yang (Yet Another Next Generation) configurationinformation, including DetNet traffic profile and flow specification, toand from the DetNet controller.

In order to process the DetNet traffic in the 5G system, the DetNet AFmay map DetNet traffic information to QoS information of the 5G systemand generate related time-sensitive communication assistance information(TSCAI). A QoS profile and the TSCAI of the 5G system generated by theDetNet AF may be used in the same way as the provision method of the TSCservice of the 5G system.

For example, 5G QoS mapped by the DetNet AF may generated as a policyrule by the PCF and then be provided to the 5G system, and the UPF mayprocess the QoS of corresponding flow according to the provided QoSpolicy rule. The access network of the 5G system may processcorresponding flow according to the QoS profile and the TSCAIinformation. With this method, the flow for the TSC service may beprocessed within the 5G system.

FIG. 5A is a diagram illustrating a mobile communication systemincluding a TSN AF that performs a function of the DetNet AF accordingto an embodiment, FIG. 5B is a diagram illustrating a mobilecommunication system including a TSCTSF that performs a function of theDetNet AF according to an embodiment, and FIG. 5C is a diagramillustrating a mobile communication system including a DetNet AFaccording to an embodiment.

According to embodiments, functions of the DetNet AF may be performed bythe TSN AF or the TSCTSF in the core network of the 5G system.

Referring to FIG. 5A, when the TSN AF includes the function of theDetNet AF, an interface between the TSN AF and the DetNet controller maybe similar to the interface between the TSN AF and the CNC. Theinterface between the TSN AF and the CNC may follow the IEEE interfacestandard, and the interface between the TSN AF and the DetNet controllermay also follow YANG data modeling language. Depending on the case, theDetNet controller may be located within the CNC, and at this time, theTSN AF may use the TSN AF-CNC interface for communication with theDetNet controller.

In an embodiment, since the TSN AF is a function on the mobilecommunication system for combination with the TSN, an Ethernet PDUsession may be supported within a 5G system and IEEE 802.1AS may besupported for the time synchronization. Therefore, in order for the TSNAF to further perform the DetNet AF function, the IP PDU session needsto be additionally supported, and the IEEE 1588 time synchronizationfunction needs to be supported together.

Referring to FIG. 5B, the TSCTSF in the mobile communication system maysupport the IP PDU sessions as well as the Ethernet PDU sessions and maysupport time synchronization services by supporting up to IEEE 1588together with IEEE 802.1AS. When the TSCTSF is connected to the DetNetcontroller and receives the DetNet traffic, the TSCTSF may need afunction to map the DetNet traffic to the 5G QoS. The TSCTSF mayaccommodate the DetNet AF function more easily than the TSN AF, but anew external interface between the TSCTSF and the DetNet controllerneeds to be supported.

Referring to FIG. 5C, When the DetNet AF makes the mobile communicationsystem function as a single DetNet node, the DetNet AF may support theIP PDU session and support the time synchronization service through somefunctions of the TSCTSF. Also, the DetNet AF may perform mapping betweenthe DetNet traffic and the 5G QoS.

FIG. 6 is a diagram illustrating a mobile communication system and aDetNet system including a TSCTSF performing the function of the DetNetAF according to an embodiment.

Referring to FIG. 6 , the TSCTSF may use a TSCTSF interface and/or anexposure interface of the mobile communication system to perform thefunction of the DetNet AF.

In an embodiment, an AF outside the core network requesting the TSCservice may request the TSC service from the TSCTSF using an exposureinterface via the NEF. When the DetNet controller is located in anexternal domain of the operator of the mobile communication system, theDetNet controller may interface using the exposure service through theNEF (Case 1).

On the other hand, a trusted AF (Trusted AF) located in the domain ofthe same operator as the mobile communication system may request aservice through an interface with the TSCTSF directly without goingthrough the NEF. Also, the DetNet controller located inside the domainof the operator of the mobile communication system may directly use theinterface with the TSCTSF without going through NEF (Case 2).

In an embodiment, the TSCTSF may process various TSC services requestedby an IP network environment except for the TSN connected in an Ethernetnetwork environment. That is, even in case of DetNet operating in the IPnetwork, the DetNet controller may request the TSC service for theDetNet traffic via the NEF or through a direct interface with theTSCTSF.

Table 1 below shows the YANG data model for the DetNet traffic.

TABLE 1 Attributes Description Comments DnFlowSpecification DetNetSourceIpAddress RFC8939 IP flow DestinationIpAddress IPv6FlowLabel DscpProtocol SourcePort DestinationPort IPSecSpi DnTrafficSpecificationInterval MaxPacketsPerInterval MaxPayloadSize MinPayloadSizeMinPacketsPerInterval DnEgressStatus None: No Egress. Ready: AllEgresses are ready. PartialFailed: One or more Egress is ready, and oneor more Egress failed. The DetNet flow can be used if the Ingress isReady. Failed: All Egresses failed. OutOfService: All Egresses areadministratively blocked FailureCode a nonzero code that specifies theerror DnFlowRequirements MinBandwidth octets per second MaxLatencyinteger number of nanoseconds MaxLatencyVariation integer number ofnanoseconds MaxLoss Packet Loss Rate (PLR) MaxConsecutiveLossTolerancethe maximum number of consecutive packets whose loss can be toleratedMaxMisordering the tolerable maximum number of packets that can bereceived out of order

In FIG. 5B, the TSCTSF may be connected to the DetNet controller througha predetermined external interface. In the interface between the DetNetcontroller and the DetNet node, data may be transmitted by the Netconfprotocol using the YANG data model and extension to the Restconfprotocol is being considered.

In an embodiment, the TSCTSF may receive data of the YANG data modeltransmitted by DetNet controller using Netconf protocol and/or Restconfprotocol as DetNet traffic information and map the DetNet flow to QoSinformation available in the 5G system based on the DetNet trafficinformation. Table 1 may represent the YANG data model of the DetNettraffic transmitted to TSCTSF by the DetNet controller.

Referring to FIG. 6 , the DetNet controller may transmit the DetNettraffic using the 3GPP interface, and at this time, the 3GPP interfacemay be provided by the DetNet controller or the AF. The DetNetcontroller may transmit the DetNet traffic by using NEF interface (e.g.,Nnef_AFsessionWithQoS service) or the TSCTSF (e.g.,Ntsctsf_QoSandTSCAssistance). At this time, DetNet traffic inputparameter needs to be added to the TSCTSF/NEF interface. The YANG datamodel in Table 1 may be included in newly added DetNet trafficparameters. The DetNet controller may change the YANG data model inTable 1 to a predetermined data exchange format (e.g., JavaScript ObjectNotation (JSON) format) using the Restconf protocol according to theservice-based interface provided by the 3GPP system, and may transmitthe DetNet traffic information to application functions (e.g., DetNetAF, TSN AF, or TSCTSF) in the mobile communication system or NEF of themobile communication system.

FIG. 7 is a diagram illustrating a DetNet information model according toan embodiment.

Referring to a DetNet information model in FIG. 7 , the DetNetcontroller may use a DetNet node and a south bound interface (SBI). Whenthe 5G system operates as the DetNet node, the DetNet controller maycommunicate with the 5G system using the same SBI. The DetNet controllermay communicate with the UPF through the TSCTSF that performs the DetNetAF function of the 5G system through the SBI. communicate with theTSCTSF through the SBI, and the TSCTSF may control the UPF to operate asthe DetNet node within the 5G system.

FIG. 8 is a flowchart illustrating a method in which the mobilecommunication system operates as a DetNet node according to anembodiment.

Referring to FIG. 8 , the TSCTSF in charge of the DetNet AF function mayreceive configuration information to operate the mobile communicationsystem as a single DetNet node from the DetNet controller of the DetNetsystem (S110).

To enable the mobile system to act as the DetNet node (e.g., a DetNetrouter) based on the configuration information received from the DetNetcontroller, the TSCTSF may configure the UPF/NW-TT and UE/DS-TT thatprocess the DetNet traffic the DetNet node (S120).

Table 2 below shows properties used to manage information of user planenodes in the 5G system. Referring to Table 2, a user plane node ID maybe used as a bridge ID when a user plane node is connected to the TSNand operates as a TSN bridge. When the 5G system is connected to theDetNet system and operates as the DetNet node, the user plane node IDmay be used as the DetNet Node ID.

TABLE 2 Attribute Description Comment DS-TT Port Port Number allocatedby the NW-TT Number for the DS-TT for a given PDU Session User planeBridge identifier of the 5GS TSN bridge, node ID or user-plane node ID,or DetNet node.

In an embodiment, the TSN AF may transmit configuration information tothe DS-TT/NW-TT by adding the configuration information for the 5Gsystem to operate as the TSN bridge to the PMIC/BMIC. The TSCTSF maytransmit the configuration information to the DS-TT/NW-TT by adding theconfiguration information to the user plane node management informationcontainer (PMIC/UMIC) that enables the DS-TT/NW-TT processing the DetNettraffic to operate as the DetNet node.

Table 3 below shows standardized port management information (PMI) andTable 4 shows standardized user plane node management information (UMI).

TABLE 3 Supported Supported Supported operations Applicabilityoperations operations by TSCTSF Port management information DS-TT NW-TTby TSN AF by TSCTSF (DetNet AF) General Port management capabilities X XR R R Time Synchronization Information TSN Time domain number X X RWSupported PTP instance types X R R R Supported transport types X R R RSupported delay mechanisms X R R R PTP grandmaster capable X R R R gPTPgrandmaster capable X R R R Supported PTP profiles X R R R Number ofsupported PTP instances X R R R PTP Instance ID X X RW RW RW > PTPprofile X X RW RW RW > Transport type X X RW RW RW > Grandmastercandidate enabled X RW RW RW > Grandmaster enabled X RW RW RW IEEE Std1588 [126] data sets > defaultDS.clockIdentity X X RW RW RW >defaultDS.clockQuality.clockClass X X RW RW RW >defaultDS.clockQuality.clockAccuracy X X RW RW RW >defaultDS.clockQuality.offsetScaledLogVariance X X RW RW RW >defaultDS.priority1 X X RW RW RW > defaultDS.priority2 X X RW RW RW >defaultDS.domainNumber X X RW RW RW > defaultDS.sdold X X RW RW RW >defaultDS.instanceEnable X X RW RW RW >defaultDS.externalPortConfigurationEnabled X RW RW RW >defaultDS.instanceType X X RW RW RW > portDS.portIdentity X X RW RW RW >portDS.portState X X RW RW RW > portDS.logMinDelayReqInterval X X RW RWRW > portDS.logAnnounceInterval X X RW RW RW >portDS.announceReceiptTimeout X RW RW RW > portDS.logSyncInterval X X RWRW RW > portDS.delayMechanism X X RW RW RW >portDS.logMinPdelayReqInterval X X RW RW RW > portDS.versionNumber X XRW RW RW > portDS.minorVersionNumber X X RW RW RW >portDS.delayAssymetry X X RW RW RW > portDS.portEnable X X RW RW RW >timePropertiesDS.currentUtcOffset X X RW RW RW >timePropertiesDS.timeSource X X RW RW RW >externalPortConfigurationPortDS.desiredState X RW RW RW IEEE Std 802.1AS [104] data sets RW RW > defaultDS.clockIdentity X X RW RW RW >defaultDS.clockQuality.clockClass X X RW RW RW >defaultDS.clockQuality.clockAccuracy X X RW RW RW >defaultDS.clockQuality.offsetScaledLogVariance X X RW RW RW >defaultDS.priority1 X X RW RW RW > defaultDS.priority2 X X RW RW RW >defaultDS.timeSource X X RW RW RW > defaultDS.domainNumber X X RW RWRW > defaultDS.sdold X X RW RW RW >defaultDS.externalPortConfigurationEnabled X RW RW RW >defaultDS.instanceEnable X X RW RW RW > portDS.portIdentity X X RW RWRW > portDS.portState X R R R > portDS.ptpPortEnabled X X RW RW RW >portDS.delayMechanism X X RW RW RW > portDS.isMeasuringDelay X X R R R >portDS.asCapable X X R R R > portDS.meanLinkDelay X X R R R >portDS.meanLinkDelayThresh X X RW RW RW > portDS.delayAssymetry X X RWRW RW > portDS.neighborRateRatio X X R R R >portDS.initialLogAnnounceInterval X X RW RW RW >portDS.currentLogAnnounceInterval X X R R R >portDS.useMgtSettableLogAnnounceInterval X X RW RW RW >portDS.mgtSettableLogAnnounceInterval X X RW RW RW >portDS.announceReceiptTimeout X RW RW RW > portDS.initialLogSyncIntervalX X RW RW RW > portDS.currentLogSyncInterval X X R R R >portDS.useMgtSettableLogSyncInterval X X RW RW RW >portDS.mgtSettableLogSyncInterval X X RW RW RW >portDS.syncReceiptTimeout X RW RW RW >portDS.syncReceiptTimeoutTimeInterval X RW RW RW >portDS.initialLogPdelayReqInterval X X RW RW RW >portDS.currentLogPdelayReqInterval X X R R R >portDS.useMgtSettableLogPdelayReqInterval X X RW RW RW >portDS.mgtSettableLogPdelayReqInterval X X RW RW RW >portDS.initialLogGptpCapableMessageInterval X X RW RW RW >portDS.currentLogGptpCapableMessageInterval X X R R R >portDS.useMgtSettableLogGptpCapableMessageInterval X X RW RW RW >portDS.mgtSettableLogGptpCapableMessageInterval X X RW RW RW >portDS.initialComputeNeighborRateRatio X X RW RW RW >portDS.currentComputeNeighborRateRatio X X R R R >portDS.useMgtSettableComputeNeighborRateRatio X X RW RW RW >portDS.mgtSettableComputeNeighborRateRatio X X RW RW RW >portDS.initialComputeMeanLinkDelay X X RW RW RW >portDS.currentComputeMeanLinkDelay X X R R R >portDS.useMgtSettableComputeMeanLinkDelay X X RW RW RW >portDS.mgtSettableComputeMeanLinkDelay X X RW RW RW >portDS.allowedLostResponses X X RW RW RW > portDS.allowedFaults X X RWRW RW > portDS.gPtpCapableReceiptTimeout X X RW RW RW >portDS.versionNumber X X RW RW RW > portDS.nup X X RW RW RW >portDS.ndown X X RW RW RW > portDS.oneStepTxOper X X R R R >portDS.oneStepReceive X X R R R > portDS.oneStepTransmit X X R R R >portDS.initialOneStepTxOper X X RW RW RW > portDS.currentOneStepTxOper XX RW RW RW > portDS.useMgtSettableOneStepTxOper X X RW RW RW >portDS.mgtSettableOneStepTxOper X X RW RW RW > portDS.syncLocked X X R RR > portDS.pdelayTruncatedTimestampsArray X X RW RW RW >portDS.minorVersionNumber X X RW RW RW >timePropertiesDS.currentUtcOffset X X RW RW RW >externalPortConfigurationPortDS.desiredState R RW RW RW

TABLE 4 Supported Supported Supported operations operations operationsby TSCTSF User plane node management information by TSN AF by TSCTSF(DetNet AF) Information for 5GS Bridge User plane node Address R R RUser plane node ID R R R NW-TT port numbers R R R Time synchronizationinformation Supported PTP instance types R R R Supported transport typesR R R Supported delay mechanisms R R R PTP grandmaster capable R R RgPTP grandmaster capable R R R Supported PTP profiles R R R Number ofsupported PTP instances R R R Time synchronization information for DS-TTports > Time synchronization information for each DS-TT port > DS-TTport number RW RW RW >> Time synchronization information for each PTPInstance >> PTP Instance ID RW RW RW >> PTP profile RW RW RW >>Transport type RW RW RW >> Grandmaster on behalf of DS-TT enabled RW RWRW IEEE Std 1588 [126] data sets >> defaultDS.clockIdentity RW RW RW >>defaultDS.clockQuality.clockClass RW RW RW >>defaultDS.clockQuality.clockAccuracy RW RW RW >>defaultDS.clockQuality.offsetScaledLogVariance RW RW RW >>defaultDS.priority1 RW RW RW >> defaultDS.priority2 RW RW RW >>defaultDS.domainNumber RW RW RW >> defaultDS.sdold RW RW RW >>defaultDS.instanceEnable RW RW RW >> defaultDS.externalPortConfigurationEnabled RW RW RW >> defaultDS.instanceType RWRW RW >> portDS.portIdentity RW RW RW >> portDS.portState R R R >>portDS.logMinDelayReqInterval RW RW RW >> portDS.logAnnounceInterval RWRW RW >> portDS.announceReceiptTimeout RW RW RW >>portDS.logSyncInterval RW RW RW >> portDS.delayMechanism RW RW RW >>portDS.logMinPdelayReqInterval RW RW RW >> portDS.versionNumber RW RWRW >> portDS.minorVersionNumber RW RW RW >> portDS.delayAssymetry RW RWRW >> portDS.portEnable RW RW RW >> timePropertiesDS.currentUtcOffset RWRW RW >> timePropertiesDS.timeSource RW RW RW >>externalPortConfigurationPortDS.desiredState RW RW RW IEEE Std 802.1AS[104] data sets >> defaultDS.clockIdentity RW RW RW >>defaultDS.clockQuality.clockClass RW RW RW >>defaultDS.clockQuality.clockAccuracy RW RW RW >>defaultDS.clockQuality.offsetScaledLogVariance RW RW RW >>defaultDS.priority1 RW RW RW >> defaultDS.priority2 RW RW RW >>defaultDS.timeSource RW RW RW >> defaultDS.domainNumber RW RW RW >>defaultDS.externalPortConfigurationEnabled RW RW RW >> defaultDS.sdoldRW RW RW >> defaultDS.instanceEnable RW RW RW >> portDS.portIdentity RWRW RW >> portDS.portState R R R >> portDS.ptpPortEnabled RW RW RW >>portDS.delayMechanism RW RW RW >> portDS.isMeasuringDelay R R R >>portDS.asCapable R R R >> portDS.meanLinkDelay R R R >>portDS.meanLinkDelayThresh RW RW RW >> portDS.delayAssymetry RW RW RW >>portDS.neighborRateRatio R R R >> portDS.initialLogAnnounceInterval RWRW RW >> portDS.currentLogAnnounceInterval R R R >>portDS.useMgtSettableLogAnnounceInterval RW RW RW >>portDS.mgtSettableLogAnnounceInterval RW RW RW >>portDS.announceReceiptTimeout RW RW RW >> portDS.initialLogSyncIntervalRW RW RW >> portDS.currentLogSyncInterval R R R >>portDS.useMgtSettableLogSyncInterval RW RW RW >>portDS.mgtSettableLogSyncInterval RW RW RW >> portDS.syncReceiptTimeoutRW RW RW >> portDS.syncReceiptTimeoutTimeInterval RW RW RW >>portDS.initialLogPdelayReqInterval RW RW RW >>portDS.currentLogPdelayReqInterval R R R >>portDS.useMgtSettableLogPdelayReqInterval RW RW RW >>portDS.mgtSettableLogPdelayReqInterval RW RW RW >>portDS.initialLogGptpCapableMessageInterval RW RW RW >>portDS.currentLogGptpCapableMessageInterval R R R >>portDS.useMgtSettableLogGptpCapableMessageInterval RW RW RW >>portDS.mgtSettableLogGptpCapableMessageInterval RW RW RW >>portDS.initialComputeNeighborRateRatio RW RW RW >>portDS.currentComputeNeighborRateRatio R R R >>portDS.useMgtSettableComputeNeighborRateRatio RW RW RW >>portDS.mgtSettableComputeNeighborRateRatio RW RW RW >>portDS.initialComputeMeanLinkDelay RW RW RW >>portDS.currentComputeMeanLinkDelay R R R >>portDS.useMgtSettableComputeMeanLinkDelay RW RW RW >>portDS.mgtSettableComputeMeanLinkDelay RW RW RW >>portDS.allowedLostResponses RW RW RW >> portDS.allowedFaults RW RW RW >>portDS.gPtpCapableReceiptTimeout RW RW RW >> portDS.versionNumber RW RWRW >> portDS.nup RW RW RW >> portDS.ndown RW RW RW >>portDS.oneStepTxOper R R R >> portDS.oneStepReceive R R R >>portDS.oneStepTransmit R R R >> portDS.initialOneStepTxOper RW RW RW >>portDS.currentOneStepTxOper RW RW RW >>portDS.useMgtSettableOneStepTxOper RW RW RW >>portDS.mgtSettableOneStepTxOper RW RW RW >> portDS.syncLocked R R R >>portDS.pdelayTruncatedTimestampsArray RW RW RW >>portDS.minorVersionNumber RW RW RW >> timePropertiesDS.currentUtcOffsetRW RW RW >> externalPortConfigurationPortDS.desiredState RW RW RW

Table 3 shows information that may be expanded in relation to the DetNetAF in the standardized PMI and Table 4 shows information that may beexpanded in relation to the DetNet AF in the standardized UMI.

Since the 5G system operating as the DetNet node may reuse the existingTSC service or time synchronization function, functions not related tothe DetNet AF, such as IEEE standard function related to TSN bridgeinformation operating in the Ethernet in the PMI/UMI table, may not bemarked.

As a time synchronization function supported to operate as the DetNetnode, IEEE 802.1AS, IEEE 1588 BC (Boundary Clock), IEEE 1588peer-to-peer TC (Transparent Clock), IEEE 1588 end-to-end TC functionsthat can be supported by the 5G system function may be used. The DS-TTand the NW-TT may process time synchronization message.

Referring to FIG. 8 , the TSCTSF may receive the DetNet trafficinformation from the DetNet controller (S130) and map the DetNet flow tothe QoS information of the mobile communication system based on theDetNet traffic information (S140).

The YANG data model may be used for the DetNet configuration and theYANG data model may be a centralized configuration model like the CNC.The DetNet configuration may be classified into topology, pathconfiguration, flow configuration, and status. The flow configurationmay include {flow identification, priority, traffic specification,encapsulation method}.

The DetNet flow input from the DetNet controller may beadded/modified/deleted in the 5G system. In an embodiment, for a DetNetIP flow, the encapsulation method of the flow configuration may have anIP value and the priority of the flow configuration may be treated asthe same value as the priority value used in the TSN. The specificattributes that the DetNet flow may have, including flow identificationand traffic specification of the flow configuration, are shown in Table5 below.

TABLE 5 Attributes Description Comments DnFlowID A unique (management)identifier is needed for each DetNet flow within the DetNet domainDnPayloadType encapsulated App-flow format Ethernet, MPLS, or IPDnFlowFormat MPLS or IP DnFlowSpecification DetNet SourceIpAddressRFC8939 IP flow DestinationIpAddress IPv6FlowLabel Dscp ProtocolSourcePort DestinationPort IPSecSpi DnTrafficSpecification IntervalMaxPacketsPerInterval MaxPayloadSize MinPayloadSizeMinPacketsPerInterval DnFlowEndpoints the start and end reference pointsof the DetNet flow by pointing to the ingress interface/node and egressinterface(s)/node(s) DnFlowRank the rank of this flow relative to range:0-255 other flows in the DetNet domain DnFlowStatus DnIngressStatusNone: No Ingress. Ready: Ingress is ready. Failed: Ingress failed.OutOfService: Administratively blocked DnEgressStatus None: No Egress.Ready: All Egresses are ready. PartialFailed: One or more Egress isready, and one or more Egress failed. The DetNet flow can be used if theIngress is Ready. Failed: All Egresses failed. OutOfService: AllEgresses are administratively blocked FailureCode a nonzero code thatspecifies the error DnFlowRequirements MinBandwidth octets per secondMaxLatency integer number of nanoseconds MaxLatencyVariation integernumber of nanoseconds MaxLoss Packet Loss Rate (PLR)MaxConsecutiveLossTolerance the maximum number of consecutive packetswhose loss can be tolerated MaxMisordering the tolerable maximum numberof packets that can be received out of order DnFlowBiDir the flow andthe corresponding reverse direction flow must share the same path

Table 6 below shows the extended PMI to support the DetNet flow in the5G system.

TABLE 6 Applicability Supported Supported (see NOTE 6) operationsoperations Port management information DS-TT NW-TT by TSN AF by TSCTSFDetNet flow general FlowID X X — RW PayloadType (IP) X X — RW FlowFormat(IP) X X — RW Flow Specification (DetNet IP flow) SourceIpAddress X X —RW DestinationIpAddress X X — RW IPv6FlowLabel X X — RW Dscp X X — RWProtocol X X — RW SourcePort X X — RW DestinationPort X X — RW IPSecSpiX X — RW Flow Status IngressStatus X X — R EgressStatus X X — RFailureCode X X — R

Each port of the TSN AF, the TSCTSF (DetNet AF), and the DS-TT/NW-TT mayhave attributes {flow ID, flow specification} to identify the DetNetflows. In addition, each port may also have a flow status attribute inorder to report the flow status.

Referring to FIG. 8 , the DS-TT/NW-TT may report status information ofDetNet flow to the DetNet AF when status report is configured (S150).For example, when the status report is configured, the DS-TT may reportthe status information of the DetNet flow to the TSCTSF (DetNet AF)through non-access stratum (NAS) signaling. The NW-TT may report theflow status to the DetNet AF via the SMF through the UPF when the statusreport is configured. If the N4 interface between the UPF and the SMF isa service-based interface, the UPF may directly transmit the flow statusinformation to the TSCTSF (DetNet AF).

FIG. 9 is a diagram illustrating information of a DetNet flow identifiedin a port of a mobile communication system according to an embodiment.

Referring to FIG. 9 , flow information identified in the port of theDS-TT/NW-TT may have flow requirements (or traffic-requirement) andtraffic specification. That is, the QoS required by the DetNet flow maybe mapped to the QoS flow of the 5G system by the TSCTSF (DetNet AF). Atthis time, at least one DetNet flow may be mapped to one 5G QoS flow.

In order to support ‘max-latency-variation’ among the properties of theDetNet flow, a jitter value related to the property may be previouslydetermined in the mobile communication system. When the jitter value isnot defined in the 5G system, the jitter value may be determined inadvance through a QoS flow or the TSCAI or as an independent value. Asvarious high-reliability and low-latency services are required, jitterinformation needs to be established in the mobile communication system.

Among the properties of the DetNet flow,‘max-consecutive-loss-tolerance’ is a characteristic that only theDetNet flow has, and the corresponding parameter may be additionallyestablished in the mobile communication system through the QoS flow orthe TSCAI or by an additional option for the DetNet.

In order to check the connectivity of the DetNet flow, the followingthree functions may be required.

1. BFD (Bidirectional Forwarding Detection) and STAMP (Simple Two-WayActive Measurement Protocol) using well-known UDP port

2. Ping, Traceroute using Internet control message protocol (ICMP)

3. Generic Routing Encapsulation (GRE)-in-UDP (Protocol Type in GREheader=0x8902)

In an embodiment, the mobile communication system may optionally providea DetNet flow management function. Among the functions for checking theconnectivity of the DetNet flow, the function using the ICMP may operatein IP packet processing of the 5G system. However, since entities of theconventional mobile communication system does not provide functions 1and 3, the DS-TT and/or NW-TT needs to provide the functions 1 and 3.

Referring to FIG. 8 , the TSCTSF (DetNet AF) may transmit parameters formanaging the connectivity of the DetNet flows to the DS-TT and/or NW-TT(S160). The DS-TT and/or NW-TT may then manage the connectivity of theDetNet flows based on the parameters for managing the connectivity ofthe DetNet flows.

Table 7 below shows PMI parameters for the DS-TT and/or NW-TT to performthe DetNet flow management and Table 8 shows UMI parameters for theDS-TT and/or NW-TT to perform the DetNet flow management.

TABLE 7 Supported Supported Supported operations Port managementApplicability operations operations by DetNet information DS-TT NW-TT byTSN AF by TSCTSF AF Reference BFD(Bidirectional X X — — RW RFC5880Forwarding Detection) STAMP(Simple X X — — RW RFC8762 Two-Way ActiveMeasurement Protocol) GRE-in-UDP X X — — RW RFC8086 (Protocol Type inGRE header = 0x8902)

TABLE 8 User plane node Supported Supported Supported managementoperations operations operations information by TSN AF by TSCTSF byDetNet AF Reference BFD(Bidirectional — — RW RFC5880 ForwardingDetection) STAMP(Simple — — RW RFC8762 Two-Way Active MeasurementProtocol) GRE-in-UDP — — RW RFC8086 (Protocol Type in GRE header =0x8902)

As described above, embodiments propose a mobile communication systemstructure that can act as a DetNet node, enabling the mobilecommunication system to integrate with DetNet to provide the timesynchronization communication and time synchronization services requiredby a wide variety of applications.

FIG. 10 is a diagram illustrating an application function according toan embodiment.

The application function according to an embodiment may be implementedas a computer system, for example, a computer-readable medium. Referringto FIG. 10 , the computer system 1000 may include at least one of aprocessor 1010, a memory 1030, an input interface device 1050, an outputinterface device 1060, and a storage device 1040 communicating through abus 1070. The computer system 1000 may also include a communicationdevice 1020 coupled to the network. The processor 1010 may be a centralprocessing unit (CPU) or a semiconductor device that executesinstructions stored in the memory 1030 or the storage device 1040. Thememory 1030 and the storage device 1040 may include various forms ofvolatile or nonvolatile storage media. For example, the memory mayinclude read only memory (ROM) or random-access memory (RAM). In theembodiment of the present disclosure, the memory may be located insideor outside the processor, and the memory may be coupled to the processorthrough various means already known. The memory is a volatile ornonvolatile storage medium of various types, for example, the memory mayinclude read-only memory (ROM) or random-access memory (RAM).

Accordingly, the embodiment may be implemented as a method implementedin the computer, or as a non-transitory computer-readable medium inwhich computer executable instructions are stored. In an embodiment,when executed by a processor, the computer-readable instruction mayperform the method according to at least one aspect of the presentdisclosure.

The communication device 1020 may transmit or receive a wired signal ora wireless signal.

On the contrary, the embodiments are not implemented only by theapparatuses and/or methods described so far, but may be implementedthrough a program realizing the function corresponding to theconfiguration of the embodiment of the present disclosure or a recordingmedium on which the program is recorded. Such an embodiment can beeasily implemented by those skilled in the art from the description ofthe embodiments described above. Specifically, methods (e.g., networkmanagement methods, data transmission methods, transmission schedulegeneration methods, etc.) according to embodiments of the presentdisclosure may be implemented in the form of program instructions thatmay be executed through various computer means, and be recorded in thecomputer-readable medium. The computer-readable medium may includeprogram instructions, data files, data structures, and the like, aloneor in combination. The program instructions to be recorded on thecomputer-readable medium may be those specially designed or constructedfor the embodiments of the present disclosure or may be known andavailable to those of ordinary skill in the computer software arts. Thecomputer-readable recording medium may include a hardware deviceconfigured to store and execute program instructions. For example, thecomputer-readable recording medium can be any type of storage media suchas magnetic media like hard disks, floppy disks, and magnetic tapes,optical media like CD-ROMs, DVDs, magneto-optical media like flopticaldisks, and ROM, RAM, flash memory, and the like.

Program instructions may include machine language code such as thoseproduced by a compiler, as well as high-level language code that may beexecuted by a computer via an interpreter, or the like.

The components described in the example embodiments may be implementedby hardware components including, for example, at least one digitalsignal processor (DSP), a processor, a controller, anapplication-specific integrated circuit (ASIC), a programmable logicelement, such as an FPGA, other electronic devices, or combinationsthereof. At least some of the functions or the processes described inthe example embodiments may be implemented by software, and the softwaremay be recorded on a recording medium. The components, the functions,and the processes described in the example embodiments may beimplemented by a combination of hardware and software. The methodaccording to example embodiments may be embodied as a program that isexecutable by a computer, and may be implemented as various recordingmedia such as a magnetic storage medium, an optical reading medium, anda digital storage medium.

Various techniques described herein may be implemented as digitalelectronic circuitry, or as computer hardware, firmware, software, orcombinations thereof. The techniques may be implemented as a computerprogram product, i.e., a computer program tangibly embodied in aninformation carrier, e.g., in a machine-readable storage device (forexample, a computer-readable medium) or in a propagated signal forprocessing by, or to control an operation of a data processingapparatus, e.g., a programmable processor, a computer, or multiplecomputers.

A computer program(s) may be written in any form of a programminglanguage, including compiled or interpreted languages, and may bedeployed in any form including a stand-alone program or a module, acomponent, a subroutine, or other units suitable for use in a computingenvironment.

A computer program may be deployed to be executed on one computer or onmultiple computers at one site or distributed across multiple sites andinterconnected by a communication network.

Processors suitable for execution of a computer program include, by wayof example, both general and special purpose microprocessors, and anyone or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random-access memory or both. Elements of a computer may include atleast one processor to execute instructions and one or more memorydevices to store instructions and data. Generally, a computer will alsoinclude or be coupled to receive data from, transfer data to, or performboth on one or more mass storage devices to store data, e.g., magnetic,magneto-optical disks, or optical disks.

Examples of information carriers suitable for embodying computer programinstructions and data include semiconductor memory devices, for example,magnetic media such as a hard disk, a floppy disk, and a magnetic tape,optical media such as a compact disk read only memory (CD-ROM), adigital video disk (DVD), etc. and magneto-optical media such as afloptical disk, and a read only memory (ROM), a random access memory(RAM), a flash memory, an erasable programmable ROM (EPROM), and anelectrically erasable programmable ROM (EEPROM) and any other knowncomputer readable medium.

A processor and a memory may be supplemented by, or integrated into, aspecial purpose logic circuit. The processor may run an operating system08 and one or more software applications that run on the OS. Theprocessor device also may access, store, manipulate, process, and createdata in response to execution of the software. For purpose ofsimplicity, the description of a processor device is used as singular;however, one skilled in the art will be appreciated that a processordevice may include multiple processing elements and/or multiple types ofprocessing elements.

For example, a processor device may include multiple processors or aprocessor and a controller. In addition, different processingconfigurations are possible, such as parallel processors. Also,non-transitory computer-readable media may be any available media thatmay be accessed by a computer, and may include both computer storagemedia and transmission media.

The present specification includes details of a number of specificimplements, but it should be understood that the details do not limitany disclosure or what is claimable in the specification but ratherdescribe features of the specific example embodiment.

Features described in the specification in the context of individualexample embodiments may be implemented as a combination in a singleexample embodiment. In contrast, various features described in thespecification in the context of a single example embodiment may beimplemented in multiple example embodiments individually or in anappropriate sub-combination.

Furthermore, the features may operate in a specific combination and maybe initially described as claimed in the combination, but one or morefeatures may be excluded from the claimed combination in some cases, andthe claimed combination may be changed into a sub-combination or amodification of a sub-combination.

Similarly, even though operations are described in a specific order onthe drawings, it should not be understood as the operations needing tobe performed in the specific order or in sequence to obtain desiredresults or as all the operations needing to be performed. In a specificcase, multitasking and parallel processing may be advantageous. Inaddition, it should not be understood as requiring a separation ofvarious apparatus components in the above-described example embodimentsin all example embodiments, and it should be understood that theabove-described program components and apparatuses may be incorporatedinto a single software product or may be packaged in multiple softwareproducts.

While this disclosure has been described in connection with what ispresently considered to be practical example embodiments, it is to beunderstood that this disclosure is not limited to the disclosedembodiments.

On the contrary, it is intended to cover various modifications andequivalent arrangements included within the spirit and scope of theappended claims.

While this disclosure has been described in connection with what ispresently considered to be practical embodiments, it is to be understoodthat the disclosure is not limited to the disclosed embodiments. On thecontrary, it is intended to cover various modifications and equivalentarrangements included within the spirit and scope of the appendedclaims.

What is claimed is:
 1. An application function comprising: a processorand a memory, wherein the processor executes a program stored in thememory to perform: receiving configuration information for configuring aDeterministic Networking (DetNet) node from a DetNet controller in aDetNet system; and configuring a user plane function (UPF), a deviceside time sensitive networking translator (DS-TT), and/or a network sidetime sensitive networking (NW-TT) in a mobile communication system asthe DetNet node.
 2. The application function of claim 1, wherein whenconfiguring a UPF, a DS-TT, and/or a NW-TT in a mobile communicationsystem as the DetNet node, the processor performs adding theconfiguration information to at least one information container andtransferring the at least one information container to the DS-TT and/orthe NW-TT.
 3. The application function of claim 1, wherein theapplication function is a DetNet application function (AF) configured tocommunicate the mobile communication system with the DetNet controllerof the DetNet system.
 4. The application function of claim 1, whereinthe application function is a time sensitive communication timesynchronization function (TSCTSF) in the mobile communication system. 5.The application function of claim 1, wherein the application function isa time sensitive networking (TSN) application function (AF) in themobile communication system.
 6. The application function of claim 1,wherein when receiving configuration information for configuring aDetNet node from a DetNet controller in a DetNet system, the processorperforms receiving the configuration information from the DetNetcontroller located in an external domain of the mobile communicationsystem via a network exposure function (NEF) in the mobile communicationsystem.
 7. The application function of claim 1, wherein when receivingconfiguration information for configuring a DetNet node from the DetNetcontroller in a DetNet system, the processor performs receiving theconfiguration information from the DetNet controller located within adomain of an operator of the mobile communication system.
 8. Theapplication function of claim 1, wherein the processor executes theprogram to further perform: receiving DetNet traffic information fromthe DetNet controller; and mapping a DetNet flow to a quality of service(QoS) flow of the mobile communication system based on the DetNettraffic information.
 9. The application function of claim 1, wherein theprocessor executes the program to further perform sending a parameterfor managing connectivity of the DetNet flow to the DS-TT and/or theNW-TT.
 10. A time sensitive networking (TSN) translator comprising: aprocessor and a memory, wherein the processor executes a program storedin the memory to perform: receiving configuration information forconfiguring a Deterministic Networking (DetNet) node from a DetNetcontroller of a DetNet system through an application function (AF) of amobile communication system; and processing a DetNet flow of the DetNetsystem based on the configuration information.
 11. The TSN translator ofclaim 10, wherein the TSN translator is a device-side TSN translator(DS-TT) located in the device side or a network-side TSN translator(NW-TT) located in a user plane function (UPF) in the mobilecommunication system.
 12. The TSN translator of claim 10, wherein theprocessor executes the program to further perform: receiving a parameterfor managing connectivity of the DetNet flow from the applicationfunction; and managing the connectivity of the DetNet flow based on theparameter.
 13. The TSN translator of claim 11, wherein the processorexecutes the program to further perform reporting, by the DS-TT, statusinformation of the DetNet flow to the application function through NASsignaling when the TSN translator is the DS-TT.
 14. The TSN translatorof claim 11, wherein the processor executes the program to performreporting, by the NW-TT, status information of the DetNet flow to theapplication function through the UPF when the TSN translator is theNW-TT.
 15. A method for processing a Deterministic Networking (DetNet)traffic, the method comprising: receiving, by an application function,configuration information for configuring a DetNet node from a DetNetcontroller in a DetNet system; and configuring, by the applicationfunction, a user plane function (user plane function, UPF), a deviceside time sensitive networking translator (DS-TT), and/or a network sidetime sensitive networking translator (NW-TT) in a mobile communicationsystem as the DetNet node.
 16. The method of claim 15, wherein theconfiguring a UPF, a DS-TT, and/or a NW-TT in a mobile communicationsystem as the DetNet node comprises adding the configuration informationto at least one information container and transferring the at least oneinformation container to the DS-TT and/or the NW-TT.
 17. The method ofclaim 15, wherein the application function is a time sensitivecommunication time synchronization function (TSCTSF) in the mobilecommunication system.
 18. The method of claim 15, wherein the receivingconfiguration information for configuring a DetNet node from a DetNetcontroller of a DetNet system comprises: receiving, by the applicationfunction, the configuration information from the DetNet controllerlocated in an external domain of the mobile communication system via anetwork exposure function (NEF) within the mobile communication system;or receiving, by the application function, the configuration informationfrom the DetNet controller located in a domain of an operator of themobile communication system.
 19. The method of claim 15 furthercomprising: receiving DetNet traffic information from the DetNetcontroller; and mapping a DetNet flow to a quality of service (QoS) flowof the mobile communication system based on the DetNet trafficinformation.
 20. The method of claim 15 further comprising transferringa parameter for managing connectivity of a DetNet flow to the DS-TTand/or the NW-TT.